Overview

This PR updates the E2E testing infrastructure to support running integration tests against multiple parallel server configurations, specifically:

1. A standard Toolbox server (port 5000).
2. A draft-enabled Toolbox server (port 5001) run with the --enable-draft-specs flag.

By verifying the SDK's behavior against both environments, we ensure robust fallback and negotiation behavior when newer protocol drafts are configured.

Changes

1. E2E Test Infrastructure & Multi-Server Orchestration

• Updated to start and monitor two separate instances of the Toolbox server process:
  • ToolboxServer1 on port 5000 (stable).
  • ToolboxServer2 on port 5001 (with --enable-draft-specs).
• Introduced a helper killServer to gracefully terminate both server processes and clean up assets.
• Added support for a second process reference.

2. E2E Test Suites

• Refactored E2E tests in both @toolbox-sdk/core and @toolbox-sdk/adk to run all test cases against both servers (localhost:5000 and localhost:5001).
• Added Protocol Configuration E2E Tests which:
  • Check that the client defaults to the correct protocol version if none is specified.
  • Verify that the client successfully negotiates and falls back to an older supported protocol (MCP_v20251125) if the target server does not support the client's configured draft protocol (MCP_DRAFT_2026_v1).

3. Protocol & Client Updates

• Removed the verbose warning in ToolboxClient's constructor that alerted when initializing with a version other than MCP_LATEST.
  • This prevents spam when fallback / auto-negotiation takes place.
  • This PR adds dual-server support and other PRs added version negotiation.
    • With that ToolboxClient automatically negotiates or falls back to older/stable supported protocol versions when connecting to servers that don't support the latest draft spec.
    • Because of that, this trigger was warning even during the expected protocol negotiation or fallback.
    • Moreover, any protocol version included in getSupportedMcpVersions() is supported by the SDK.
    • If a user or internal transport explicitly targets a supported protocol version, it is valid behavior and shouldn't emit a warning.

5. Unit Test Adjustments

• Equipped MockTransport in client/tool unit tests with a mock protocolVersion property to satisfy current transport interface requirements.
• Removed obsolete assertions in unit tests checking for the deleted MCP_LATEST console warnings.